*************************************************** ** NP00644 FILE ** ** DATE = 01/24/97 ** PHONE = 8-444-0017 ** CONTACT = SANDY PETERSON ** C/T = RD0011 ** USER = SANDYPE NODE = RALVM29 ** *************************************************** APARTXT NA02683 = On later V1R3 and V1R4 machines X.25's internal trace facility is not working. fails with "xmonitor: failed opening message text file "xmonitor.cat" " APARTXT NA02546 = If 6611 sdlc port using a modem goes down and then back up the 6611 will take a dump and then reboot. APARTXT NA02637 = first time customer logs in with default id 6611c, integrity group requires we force a password change. APARTXT NA02560 = Internal Enhancements for NP00640 APARTXT NA02595 = Unplug the cable first time caused the LQM decide fail after missedReport 3 times, it works fine. However, plug back cable and unplug it again caused the LQM deceide to fail immediately without reaching missedReport 3 times. The LCP state indicated that it is still in OPEN state. APARTXT NA02603 = On the TEST Command all routes broadcast response, DLS is settin g the RIF field in the route it saves for connection to the MAC address. APARTXT NA02604 = When configuring a PU in a VTAM Switched Major Node to a dependent LU connected to a 6611 by Ethernet, the architecture specifies that both the mac and sap address must be entered in the canonical format. Currently the mac address must be entered in the non-canonical format. Following the application of this APAR, both the mac and sap address should be entered in the canonical format in the VTAM Switched Major Node path statement, as the architecture specifies. APARTXT NA02605 = Current file size of pd_ipxd.tables set in sysmon.file is 1M which is too small for customer's ipx networks (about 1.4M). So when customer generated an ipx dump to serach for the server names, customer could not view the file because the file has been pruned and became 0 bytes in content. APARTXT NA02607 = Internal Enhancements for NP00625 APARTXT NA02610 = A timing problem was encountered at the State of Georgia account where one router believes he is in OSPF Full state with another router who believe he is in OSPF Exstart state. APARTXT NA02609 = Negative NetBIOS name caching not working right for all network configurations. APARTXT NA02611 = appn view -APPC gives list of sessions and modes for sessions that were active at some time in the node, and not sessions that are currently active APARTXT NA02666 = callout via compliant dlsw 2210 partner fails. APARTXT NA02638 = Internal Enhancements for NP00642 APARTXT NA02685 = LSA messages should contain more information to facilitate 2210 and OEM router debug. APARTXT NA02641 = The problem is related to the specific FR point-to-point configu defined on the router. The 6611 has supported multiple IP addres on a given interface, but in this configuration, there are multi IP addresses on the serial interface and each is the same. Becau of this, the MIB logic that handles the ipAddressTable is defici and gets into an infinite loop when it comes to this interface w duplicate addresses. APARTXT NA02667 = /testbin/ospf_sock should allowing more filtering of IP and OSPF header output. APARTXT NA02668 = K ping from Windows/95 will kill AIX. Possibly MPNP as well. Fix ported from Austin AIX development. APARTXT NA02669 = Often, with more than 1 X.25 adapter in a V1R4 6611, the X.25 adapters would not boot properly. They'd never boot properly with 4 X.25 adapters. Pings would show the problem quickly. Also, "lsdev -G|grep x" would show apmx0 would not match with x25s0, and apmx1 would not match with x25s1, etc. APARTXT NA02644 = pd_sysmon.trc shows repeated restarts of GateD daemon even though it is already started. It is believed that sysmon gets ahold of a pid number that is not correct for GateD and loops on a GateD process restart when in fact GateD is already running. Local Fix: Reboot the router APARTXT NA02670 = Mondisk moving files caused pd_x25d.out files handles to be lost by x25d.c and no further debug output would be written to pd_x25d.out. Now it is. Also see more device names written so facilitate understanding multiple adapter scenarios. APARTXT NA02678 = A customer was losing mbufs, and the router would eventually lock up. It was a very slow loss. Traces showed AppleTalk NBP and ZIP frames were lost. The customer had configured AppleTalk on all the links, but was not using it. The links were configured as non-seed. The problem is in at_input.c where received AppleTalk frames that weren't RTMP frames were not being freed when the link was in a "need seed" state. I am also submitting changes to at_tree.c for another mbuf loss problem, plus util.c and k_mib.c in the atd daemon for an atd growth problem. APARTXT NA02658 = Internal Enhancements for NP00602 APARTXT NA02660 = v1r4 only tries for 5 minutes to start an x.25 connection. If the connection does not start, only recourse is to reboot 6611 to try again. This mostly is true for back-to-back connections. True network connections would not normally encounter this problem. APARTXT NA02679 = pd_x25d.out gets pruned at 10000 bytes. That is not enough. APARTXT NA02680 = code hangs in PEfree_ips when dialog lock held APARTXT NA02681 = only changing sccs_id and bogus comment in dls/sysx/dlc/Makefile, so there's nothing to test other than making sure it builds. APARTXT NA02662 = No code to handle PING that is larger than MTU defuned on card. APARTXT NA02663 = Token-Ring EIB will stop receiving frames but will continue to transmit. This will happen on the old or the cost reduced token- ring adapter. This problem will be seen when the adapter receives a jabber frames. Currently this frames are not discarded by the daughter card which causes a standoff situation between the adapter and daughter card code (since all the buffers are used up by the daughter card waiting for adapter to release buffers, which it does not since its low water mark is not reached and awaits completion of current (ie. jabber) frame).. This fix in daughter card code will handle such a situation by dropping jabber frames (releasing buffers). APARTXT NA02686 = inventory changes for r4ap level fx64202 APARTXT NA02682 = When a LSA gets stuck on a retransmission queue and the timer goes off the regenerate all the summary LSA's, a core dump can occur. APARTXT NA02665 = Another router who's mtu is set excessively large sends ospf frame and 6611 gated crashes along with truncating. APARTXT NA02671 = fast path command dls debug view -c no longer shows dls q numbers. The q number could then be correlated with the q number on dls partners command to see what partner the conversation was connected to. WIth the removal of the q's, customer has no way to determine what partner is involved. APARTXT NA02672 = module xxxmss00 abends on a free of location 0, entry is in the error log, problem occurs on np00625, np00640, np00623. Does not occure if fx62501 through fx62503 are applied. APARTXT NA02674 = th byte of submask clobbered for ip secondary addresses APARTXT NA02696 = From Config. tool, one can configure up to 64 ip addresses over X.25 port (the default is 20). But through System Manager, Configuraton--System Manager Configuration Utility -- Add Configurati on Element to a list object---port level---X.25 adapter--list of IP Para meters of X.25. only up to 13 IP/X.25 mapping is allowed which is not adequate. APARTXT NA02697 = Internal Enhancements for NP00627 APARTXT NA02698 = boot 6611 with single X.25 adapter. Before fix for 22951, sending in a configuration from config tool would not work -- X.25 adapter would not reconfigure as indicated by method errors in pd_sysmon.trc and other problems. APARTXT NA02699 = Pexit in an appn component APARTXT NA02700 = Symptom is not recreatable in lab. Need to have DCE with congestion which eventually leads to restarting multiple logical channels. Just make sure X.25 comes up OK. APARTXT NA02693 = gated is crashing with dumps when configured and used in a BGP-4 situation. Appears to be choking on bad subnet/net masks. APARTXT NA02704 = Pexit in cswdxrcv. APARTXT NA02703 = There is a problem in formating kernel trace using ospf_sock tool (option -t). APARTXT NA02713 = OSPF ASE routes with the same LSID are sometimes stored in the wrong order causing the wrong one to be selected. APARTXT NA02701 = PSNA load through 6Oct96C 4Nov96C 23 Nov96C 3Dec96C APARTXT NA02702 = Build break - undefined symbols BITTEST and BITTEST_BYTE APARTXT NA02705 = Area border router is, at times, failing to send summary upadate to certain stub areas. Once it gets in this condition, a reset of gated is required. Condition seems to be brought on by intermittent loss of connectivity to the stub area. APARTXT NA02714 = Add option to dlstools to clear a conversation based on Data Link Correlator and do some checking before the conversation is cleared. Using this option, conversations in steady states, connected and circuit established, cannot be cleared. Also, the conversation must be 'stuck' in its current state for a period of time. This option will prevent someone from clearing the wrong conversation using the Data Link Correlator. APARTXT NA02709 = Sometimes the X.25 post-proto.start scripts would run before the proto.start scripts (you'd have to look at pd_sysmon.trc to detect this). This would sometimes cause X.25 startup failure. You'll need reboot maybe 10 or 15 times to make sure this works since timing windows are involved. I think I've closed them now. Regards, Bob Koury APARTXT NA02715 = The customer Caremark is getting stuck in state 21 (Halt LS No Ack) s ince switching to rfc1795 compliant code. Following is the scenario for what is happening. A CUR_ex is received by the Analyst, who LANCASTs a TESTFRAME to all four DLSw LAN ports. (This is significant because to hit this problem you need multiple LAN ports, AND more then one of them that "can reach" the de stination MAC.) The four Lanwrites send out TEST commands and all four get TEST responses. As the TEST responses are processed by Lanread, a DLC_HALT_LS is issu ed back to the LLC because this is an explorer flow, and a RESPFRAME is sent bac k to the Analyst. The first RESPFRAME is received by the Analyst and generate s a ICR_ex back to the remote side. The following three RESPFRAMEs are received and since a match is not found in the OSCUR database for these, the Analyst gen erates a HALTLS_NOW message back to Lanwrite to clean up the link station beca use this is an extra, unneeded conversation. Well, since this is an explorer flo w, the link station has already been cleaned up. But, because some other unrelat ed link station might have been started in the mean time, using the now unused link s tation correlator that is listed in the HALTLS_NOW, when the Lanwrite gets t he HALTLS_NOW, it sends a DLC_HALT_LS for this new link station and puts it in state HALTLS_NO_ACK. The GDLC that is passed with the HALT_LS is for some other, unrelated link stations (GDLCs are unique per port, ie GDLC 1 on port 1 refers to a different LS then GDLC 1 on port 2), so when the STAH_RES comes back, the "DLSw" LS ID is diff erent that the one given on the HALT_LS. Thus, the original LS put in HALTLS_NO_ACK will remain there forever, plus another unrelated conversation is halted for no r eason. This defect only relates to RFC 1795 code, so should not be migrated to v1r3_p383fx!!!! APARTXT NA02712 = Internal Enhancements for NP00627 APARTXT NA02744 = When LANREAD receives a DLC_STAS_RES exception while in HALTLS_NO_ACK state, it sends a message with type 0 to its DLSw partner. No message should be sent when in this state. APARTXT NA02716 = On activation, gated exits with a parsing error on the gatedtrace.ctl file. Router is up, but no gated. APARTXT NA02754 = With new Tama data center, some OSPF ABRs go to 100 percent utilization when many routers are brought up and down. APARTXT NA02718 = Bootp reply is being corrupted. APARTXT NA02745 = Configuring an IP udp parm caused srb to become disabled. Also, configuring on any port that had both TB and SRB configured a parm that would not cause a reboot for 1 bridge type would cuase the other to be disabled. APARTXT NA02746 = Allow reception only of OSPF Hello and RIP packets multicast packets over frame relay to support PPP<->Frame Relay translation devices such as 2219 (IBM re-marketed Sync Research) box. APARTXT NA02759 = Basic IP filtering doesn't work in the V1R4 Enhanced Function PTF stream. This includes NP00640 and NP00642 thru FX64203. Non-symmetric and special TCP/UDP filtering does work however. APARTXT NA02768 = Internal Enhancements for NP00644 ENDSET COMPID FOR PTF NP00644 = 564801600,140 PRODID FOR PTF NP00644 = 5648016,Multiprotocol Network Program PREREQ FOR NP00644 = NONE ENDSET COREQ FOR NP00644 = NONE ENDSET SUP FOR NP00644 = NONE ENDSET IFREQ FOR NP00644 = NONE ENDSET MEMO TO USERS = | | | MEMO FOR NP00644 | | | +---------------------------------------------------------------+ CONTENTS OF THIS MEMO _____________________ o Description of Supersede and Prerequisite PTFs o Installation instructions for NP00644 o Engineering PTFs with contents included in Production PTFs o New Function Contained in PTF NP00642/640 - SMDS IPX, IP - SDLC Switched Dial In - UDP Broadcast Forwarding (IPHelper) - Option set 1116 - NNS support for DLUR EN - BGP-4 - Multiple IP Addresses - IP Filters - Router Access via Bridged EN Port - APPN APING - IPX PACING AND LARGER SAP/RIP TABLES - Bridge Priority Queueing - System Manager Enhancements - Configuration Enhancements SUPERSEDE AND PREREQUISITE PTFS ________________________________ NP00644 is not a supersede PTF. There are no prerequisite PTFs for NP00644. Any user at base V1R4 can apply this ptf. Having PTFs NP00620, NP00623, NP00625, NP00627, NP00640 or NP00642 though not required, will not prevent NP00644 from being applied. All the fixes contained in NP00640, NP00642, NP00627, NP00625, NP00623 NP00620 are contained in NP00644. Users at any release levels other than V1R4 must migrate to that level (using NP99932 or NP99931) and be committed at that level before applying NP00644. Note: NP99932 is an MES Upgrade to V1R4 at PTF level NP00625. NP99931 is an MES Upgrade to V1R4 base. PTF INSTALL INSTRUCTIONS FOR NP00644 ____________________________________ Potential problems or delays in the installation procedure can be avoided if you perform certain actions first. CLEANING UP THE 6611 TRANSFER DIRECTORY Receiving installation files places them in the transfer directory of the 6611. If you know you have unnecessary files in the transfer directory (such as outdated dumps or reports), delete the files before beginning the installation. Refer to "Delete Transfer Directory Files" in the Operations chapter of the IBM Multiprotocol Network Program Operations and Problem Management manual for details. STOPPING TRACES Before beginning the installation process for any update, stop all trace activities. Active traces might cause installation to fail because of insufficient space. Refer to the Problem Determination chapter of the IBM Multiprotocol Network Program Operations and Problem Management manual for information on stopping traces. In particular, it is important that IP routing (gated) protocol traces should be stopped before installing this PTF. HANDLING DEVELOPMENT PTFS Before beginning the installation process for any software update, check to see if you have any development PTFs on your system. Development PTFs may be identified as containing the characters FX in their names, for example: Name: mpnp.obj NP00001 ---------------------- Fix ID Release ========================== FX00001 01.01.0000.0001 If you know that you have development PTFs on your system, call your IBM Support Center and provide the following information: o The development PTFs that are already on your system o The software updates you wish to install INSTALLING SOFTWARE UPDATES Software updates are installed from the transfer directory using the Software Installation and Maintenance Facility of the Multiprotocol Network Program V1R3 Supplement(SD35-0238). This is a multiphase process that permits the software updates to be tested before making them a permanent part of the Multiprotocol Network Program. When updating software, the first step after importing the software update is to apply the software update. After a software update is applied to a 6611, it can be activated at a later time. You can specify the maintenance level and the date and time of the activation. The 6611 will be re-IPLed at activation time. Thus, the application of a PTF is not directly coupled with the re-IPL of the router. Any software update that is applied, but not activated in the currently running 6611, can be rejected at any time. A software update must be active before it can be committed. Warning: When you commit the software update, the change is permanent. There are several rules to consider when installing software updates that have dependencies: o Software updates cannot be applied until their prerequisite software updates have been applied. o Applied software updates cannot be committed until their prerequisite software updates have been committed. Possible Messages When Applying PTFs: If there is not sufficient space available, you will see a system message similar to: Installation failed. Please press enter to view the detailed information. (Assuming Enter is pressed, this detailed message is displayed:) installp could not complete because there is not enough space in file system /usr. It needs 476 more 1K blocks. The space available in /usr is less than the minimum required for this operation. The selected install operation will not be started now. Press Enter to continue. If there are more than 1000 1K blocks free in each file system, then you will see different messages depending on whether there was sufficient room for the PTFs you selected to apply. NOTE: If you have insufficient space in the file systems other than /tmp and you have commited all prior PTF's, you must contact IBM service. IBM service will make the appropriate adjustments to the file systems. If you select multiple PTFs to be applied and there is room for some, but not all, only the ones that fit will be applied. The log file pd_update.log in the transfer directory will inform you of this. To perform software updates from the System Manager: 1. Log in to the System Manager using a controlling user ID. 2. Select Software Installation and Maintenance on the System Manager main menu. Follow this procedure to install your software update using the System Manager: Step 1 Your software update is sent to you on diskettes or tape. The software update must be moved to the transfer directory for installation. Before proceeding, refer to "Recommended Software Pre-Installation Actions" for suggested actions if you have not already done so. Step 2 Select Receive Software Updates from the Software Installation and Maintenance menu to move the update files to the transfer directory in the 6611. These import methods are available: * FTP * Modem * Tape * Diskette Before receiving any software files, the system validates that enough space is available in the transfer directory. NOTE: Steps 3 and 4 are optional steps for informational purposes only and are not required for this installation Step 3 Select List Software Updates in the Transfer Directory to view a list of the software in the transfer directory of the 6611, Step 4 Select List All Problems Fixed by Software Updates to list the problems fixed by the software updates in the transfer directory. Step 5 Select Apply Software Updates to install the software updates on the 6611. The installation ends without a re-ipl, and you are returned to the Software Installation Maintenance menu. Step 6 Select Activate Applied Software Updates to activate the applied software updates. In the first selection screen, select NP00644. In the second selector screen you must use "none" as a selection if that is the only choice or if you wish to select no EPTF's. COMMITTING THE SOFTWARE UPDATE (PTF NP00644) CAUTION: When you commit the software update, the change is permanent. You will not be able to reverse the commit. When PTF NP00644 is committed, underlying PTFs are committed also. All EPTFs(FX....) are rejected when NP00644 is committed. Step 1 Select Commit Active Software Updates to commit the activated software updates. Refer to Chapter 5 "Software Installation and Maintenance" in the Multiprotocol Network Program Supplement Version 1 Release 3 (SD35-0238) more installation information. ------------------------------------------------------------ Installation of PTF NP00644 along with the prerequisite and corequisite PTF's, will alleviate the need for the engineering PTF's listed below to reside on your machine. NOTE: If you are currently running with an Engineering PTF that is not on the list below, contact your IBM Service representative for possible additional instructions. FX62001 FX62002 FX62301 FX62302 FX62303 FX62501 FX62502 FX64001 FX64201 FX64202 FX64203 The Functional Enhancements described below were available in PTF NP00642/640 unless otherwise noted. All functional enhancements in NP00642/640 are also available in NP00644 which replaces NP00642... ----------------------------------------- * NNS support for DLUR EN - Option Set 1116 ----------------------------------------- This feature enables the 6611, when configured as an APPN NN, to understand when a DLUR EN that supports Option Set 1116 registers its LUs. The Dependent LU Requestor (DLUR) architecture has been enhanced to allow DLUR End Nodes to register their LUs with a Network Node Server so that searches do not need to take place each time. This can cut down significantly on unneeded network searches. The 6611 cannot be configured as an End Node but now has the Network Node Server support to receive the LU registration and recognize the LU as a DLUR LU. ----------------------------------------- * BGP-4 ----------------------------------------- Border Gateway Protocol (BGP) uses policies to control the advertisement of routes across organization (autonomous system) boundaries. Thus BGP is used to interface an organization's network with one or more providers of Internet service. BGP is also used by service providers to interface with each other. Note that BGP can also be used to control the distribution of route topology information within a large private network. BGP-4 is described in RFC-1657. The key difference between it and BGP-3 has to do with aggregation of routes. With BGP-3 all advertisements must be for classical network addresses. BGP-4 allows contiguous addresses to be aggregated. Any address prefix can be advertised as long as the advertiser provides routes to all the included addresses. So the hope is that providers will be able to aggregate the network addresses of their users and reduce the large number of routes that must be advertised today for complete information about large networks. BPG-4 also facilitates CIDR (Classless Inter-Domain Routing) since it allows an organization to advertise a block of class C networks with a single advertisement. CIDR was shipped on the 6611 in V1R4. The 6611 implementation of BGP-4 has the following limitations: - It does not support the full Internet routing table (35-40,000 routes). - The BGP-4 MIB is supported as SNMPv1 rather than SNMPv2 as specified in the RFC. ----------------------------------------- * SMDS Integration (IP and IPX) ----------------------------------------- Switched Multimegabit Data Service is a high performance, connection-less, public switched data service designed to interconnect LANs and provides LAN-like features and performance across Wide Area Networks. SMDS uses cell relay switching technology. Generic system requirements are defined in Bellcore specification TR-TSV-000722. RFC-1209 defines the handling of IP and ARP packets and encapsulation, and SMDS complies with IEEE standard 802.6 MAN. The service provides individual, group and ARP addresses at DS1 (1.5Mbps), DS3 (45Mbps) and SONET (155Mbps) speeds. It also supports a slower speed option of 56-64Kbps. The 6611 supports speeds from 56Kbps through DS1. SMDS was initially shipped on the 6611 as a PRPQ (Programming Request for Price Quotation). In PTF NP00640, the code was incorporated into the mainstream 6611 MPNP code and supported IP only. In PTF NP00642, SMDS supports IPX as well as IP. The SMDS WAN protocol can be configured on A25 or A47 two or four port serial adapters or on either LAN/WAN combo adapter. It is not supported on the old serial adapters. **************************************************************** *SUPPLEMENT TO 6611 NETWORK PROCESSOR OPERATION POCKET GUIDE * **************************************************************** **************************************************************** *** If you receive this document in softcopy format and *** *** print it, symbols, for example, in fast path commands, *** *** may not resolve accurately for some printers. Please *** *** refer to the IBM MPNP Operations and Problem Management *** *** Guide, SC31-6691 for a description of how to use these *** *** commands. *** ***************************************************************** This chapter supplements the information in Chapter 4 of the 6611 Network Processor Operation Pocket Guide, GX27-3909. These guidelines describe how fast-path commands are structured: * Brackets ([ ]) surround: - Groups of options separated by an |, when only one option in the group can be specified (for example, [-diskette|-tape]) - Groups of options separated by an &|, when one or more options in the group can be specified (for example, l(-packet) &| -frame]) * Parameters are in double quotation marks (" "). * Parentheses (( )) surround any defaults for the subobjects, actions (depending on the subobject), and options. * Braces ({ }) surround options and parameters that are not required. *************************************************************** SMDS Commands Use the SMDS commands to: * View the SMDS ARP Tables * Delete all entries from the SMDS ARP Tables * Clear SMDS statistical counters * View the SMDS individual address, group address and ARP address associated with a given interface * View the SMDS statistics for a given interface * List interfaces configured for SMDS * View the SMDS MIB Error table for a given interface Object Abbreviations: smds: SMDS, sm Subobject Abbreviations: address: addr, ad arp: a statistics: statistic, stat, s Action Abbreviations: clear: clr, c delete: del, d list: l view: v Option Abbreviations: -active: -act, -a -all -IP -ip -IPX -ipx -miberr: -me Summary of SMDS Commands smds address (view){-log} "interface" - View the SMDS individual address, group address and ARP address associated with a given interface. smds arp delete [(-all)|-IP|-IPX] "interface" - Delete entries from the SMDS ARP Tables. smds arp (view) {-log} [(-IP)|-IPX] "interface" - View the specified SMDS ARP Table. smds list {-active} {-log} "interface" - List the serial interfaces configured for SMDS. smds statistics clear "interface" - Clear SMDS statistical counters. smds statistics (view) {-log} "interface" - View the SMDS statistics for a given interface. smds statistics (view) -miberr {-log} "interface" - View the SMDS MIB Error table for a given interface. ----------------------------------------- * Multiple IP Addresses (MIA) ----------------------------------------- Prior to this function, the 6611 supported only one IP address per physical interface. This function supports multiple IP addresses on single token ring and ethernet ports. The 6611 implementation of MIA has the following limitations: - MIA is only supported on LAN adapters (token ring and ethernet). - A maximum of 10 IP addresses is allowed per physical interface with a total of 66 addresses per router. The network (sub-network) portion of the secondary address of each interface must be unique within the router. - Each IP address may have its own subnet mask. - No subnet overlapping is permitted. This restriction does not apply to the loop-back address (127.0.0.1) or the multicast address (224.0.0.x). ----------------------------------------- * IP Filters ----------------------------------------- This function allows a customer to enable traffic such as telnet and ftp (both requests and responses) to flow in one direction but not in the other. An example would be where a user might want to telnet/ftp out to the Internet but where the customer might want to restrict external access into his/her network. Customers can now choose filtering based on TCP/UDP source port, destination port or both. Prior to NP00640, filtering had to be symmetrical, that is, the restrictions had to be the same in both directions. ----------------------------------------- * Router Access via Bridged EN Port ----------------------------------------- A bridged Ethernet port can be accessed via telnet for the purposes of logging into the box. Prior to this PTF, this function was only available on token ring ports. ----------------------------------------- * SDLC MIB ----------------------------------------- Ther are two new SNMP SDLC traps that provide port and link station (LS) status. Port UP/DOWN status has also been made more accurate. Note that this function was also provided in V1R4 via PTF NP00623 and in V1R3 via PTF NP00387. ----------------------------------------- * APPN APING ----------------------------------------- An "APING" can be issued from a 6611 to any other APPN device supporting APING including another 6611, VTAM or Comm Manager/Server. APING may also be issued from one of these latter devices to a 6611. The target device does not have to be physically adjacent to the originator as long as an APPN "route" is active between the two devices. APING can be issued from a 6611 via the System Manager fastpath or a via a System Manager screen. ----------------------------------------- * IPX Pacing and Larger SAP/RIP Tables ----------------------------------------- IPX has been enhanced to provide SAP and RIP tables with 4096 entries which is twice the size of the tables in V1R4 and prior releases. In addition, IPX SAP and RIP pacing has been added to the PPP interface. ----------------------------------------- * Bridge Priority Queueing ----------------------------------------- This function provides bridge filtering that can be applied to determine the priority of SEND frames as high/medium/low. ----------------------------------------- * Switched SDLC Dial In ----------------------------------------- Allows PU Type 2.0 dial in to a 6611. ----------------------------------------- * UDP Broadcast Forwarding ----------------------------------------- This function (also know as IPHelper) allows configuring a destination address rather than a local port address as the target for forwarded UDP broadcast packets. Thus one can configure the DHCP/BOOTP server address as the target for a DHCP/BOOTP client and not worry about either the path to the server or the increased broadcast traffic on intermediate networks. ----------------------------------------- * System Manager Enhancements ----------------------------------------- The System Manager has been enhanced to provide screen and fastpath commands for APPN network debugging and other functions. Note that APPN fastpath commands were also provided in V1R4 PTF NP00623. ----------------------------------------- * Configuration Tool ----------------------------------------- The 6611 Configuration Tool has been enhanced to support the new functions in PTF NP00644. The current PTF level of the V1R4 Configuration Tool is NP00668. This Tool may also be used to configure all 6611 V1R4 routers. A Configuration UPGRADE is NOT required. The customer is warned if he/she attempts to configure function only available in PTFs NP00640, NP00642 or NP00644. In most cases, if the customer chooses to ignore this warning and configures enhanced function on a V1R4 router without the appropriate Enhanced Function PTF (NP00640-NP00644), the new function will be ignored -- however, this is not guaranteed. Additional information specific to the new Configuration Tool can be found in the README file on the Configuration Tool installation diskettes. END OF MEMO - NP00644 ENDSET LABELTXT Selective Fix Package For use on MPNP V1, R4.0 only ENDSET ***************************************************